Repository navigation
ci: skip CI on draft PRs; marking a PR ready starts it - #185
Merged
Merged
Conversation
Every job that runs on a pull request is skipped while the PR is a draft (job-level if:, so a skipped job still reports). The pull_request trigger lists ready_for_review, so marking a PR ready starts the run; every push after that runs it again and cancels the older run. Pushes, dispatches and tags are unchanged. The agent doc says to mark a PR ready to get checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CI no longer runs on draft PRs: it starts when the PR is marked ready for review, and runs on every push after that.
ci.yml:check(hosted, devenv, clippy/tests/wasm, ~60 min ceiling) is skipped on a draft. No required checks onmain.if: github.event_name != 'pull_request' || github.event.pull_request.draft == false, combined with&&and parentheses where a job already had anif:. It is a job-level skip, not a trigger filter, so a skipped job still reports.pull_requesttrigger listsopened, synchronize, reopened, ready_for_review. Concurrency is unchanged: per-PR group, a newer push cancels the older run, and marking ready replaces the all-skipped draft run.How tested
actionlinton the changed workflows. This PR is not a draft, so its own CI runs.🤖 Generated with Claude Code